Storage Network with System Registry File Verification

ABSTRACT

A processing system of a storage network operates by: generating a request for a plurality of system registry files; receiving the plurality of system registry files via a network; generating a verification indicator based on an integrity check of the plurality of system registry files versus system registry integrity data corresponding to the plurality of system registry files; and storing the system registry files in memory when the verification indicator indicates that verification was successful.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. § 120 as a continuation of U.S. Utility application Ser. No.16/986,599, entitled “VERIFYING SYSTEM REGISTRY FILES IN A STORAGENETWORK”, filed Aug. 6, 2020, which is a continuation of U.S. Utilityapplication Ser. No. 16/145,481, entitled “VALIDATING SYSTEM REGISTRYFILES IN A DISPERSED STORAGE NETWORK”, filed Sep. 28, 2018, issued asU.S. Pat. No. 10,748,055 on Aug. 18, 2020, which is a continuation ofU.S. Utility application Ser. No. 15/262,808, entitled “VALIDATINGSYSTEM REGISTRY FILES IN A DISPERSED STORAGE NETWORK”, filed Sep. 12,2016, issued as U.S. Pat. No. 10,157,094 on Dec. 18, 2018, which is acontinuation-in-part of U.S. Utility application Ser. No. 15/058,408,entitled “ACCESSING COMMON DATA IN A DISPERSED STORAGE NETWORK”, filedMar. 2, 2016, issued as U.S. Pat. No. 10,037,171 on Jul. 31, 2018, whichclaims priority pursuant to 35 U.S.C. § 119(e) to U.S. ProvisionalApplication No. 62/154,886, entitled “BALANCING MAINTENANCE AND ACCESSTASKS IN A DISPERSED STORAGE NETWORK”, filed Apr. 30, 2015, all of whichare hereby incorporated herein by reference in their entirety and madepart of the present U.S. Utility patent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION Technical Field of the Invention

This invention relates generally to computer networks and moreparticularly to dispersing error encoded data.

Description of Related Art

Computing devices are known to communicate data, process data, and/orstore data. Such computing devices range from wireless smart phones,laptops, tablets, personal computers (PC), work stations, and video gamedevices, to data centers that support millions of web searches, stocktrades, or on-line purchases every day. In general, a computing deviceincludes a central processing unit (CPU), a memory system, userinput/output interfaces, peripheral device interfaces, and aninterconnecting bus structure.

As is further known, a computer may effectively extend its CPU by using“cloud computing” to perform one or more computing functions (e.g., aservice, an application, an algorithm, an arithmetic logic function,etc.) on behalf of the computer. Further, for large services,applications, and/or functions, cloud computing may be performed bymultiple cloud computing resources in a distributed manner to improvethe response time for completion of the service, application, and/orfunction. For example, Hadoop is an open source software framework thatsupports distributed applications enabling application execution bythousands of computers.

In addition to cloud computing, a computer may use “cloud storage” aspart of its memory system. As is known, cloud storage enables a user,via its computer, to store files, applications, etc. on an Internetstorage system. The Internet storage system may include a RAID(redundant array of independent disks) system and/or a dispersed storagesystem that uses an error correction scheme to encode data for storage.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a dispersed ordistributed storage network (DSN) in accordance with the presentinvention;

FIG. 2 is a schematic block diagram of an embodiment of a computing corein accordance with the present invention;

FIG. 3 is a schematic block diagram of an example of dispersed storageerror encoding of data in accordance with the present invention;

FIG. 4 is a schematic block diagram of a generic example of an errorencoding function in accordance with the present invention;

FIG. 5 is a schematic block diagram of a specific example of an errorencoding function in accordance with the present invention;

FIG. 6 is a schematic block diagram of an example of a slice name of anencoded data slice (EDS) in accordance with the present invention;

FIG. 7 is a schematic block diagram of an example of dispersed storageerror decoding of data in accordance with the present invention;

FIG. 8 is a schematic block diagram of a generic example of an errordecoding function in accordance with the present invention;

FIG. 9A is a schematic block diagram of an embodiment of a dispersed ordistributed storage network (DSN) in accordance with the presentinvention;

FIG. 9B is a schematic block diagram of an embodiment of a dispersed ordistributed storage network (DSN) in accordance with the presentinvention; and

FIG. 10 is a logic diagram of an example of a method of validatingsystem registry files in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a dispersed, ordistributed, storage network (DSN) 10 that includes a plurality ofcomputing devices 12-16, a managing unit 18, an integrity processingunit 20, and a DSN memory 22. The components of the DSN 10 are coupledto a network 24, which may include one or more wireless and/or wirelined communication systems; one or more non-public intranet systemsand/or public internet systems; and/or one or more local area networks(LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of storage units 36 that may belocated at geographically different sites (e.g., one in Chicago, one inMilwaukee, etc.), at a common site, or a combination thereof. Forexample, if the DSN memory 22 includes eight storage units 36, eachstorage unit is located at a different site. As another example, if theDSN memory 22 includes eight storage units 36, all eight storage unitsare located at the same site. As yet another example, if the DSN memory22 includes eight storage units 36, a first pair of storage units are ata first common site, a second pair of storage units are at a secondcommon site, a third pair of storage units are at a third common site,and a fourth pair of storage units are at a fourth common site. Notethat a DSN memory 22 may include more or less than eight storage units36. Further note that each storage unit 36 includes a computing core (asshown in FIG. 2, or components thereof) and a plurality of memorydevices for storing dispersed error encoded data.

In various embodiments, each of the storage units operates as adistributed storage and task (DST) execution unit, and is operable tostore dispersed error encoded data and/or to execute, in a distributedmanner, one or more tasks on data. The tasks may be a simple function(e.g., a mathematical function, a logic function, an identify function,a find function, a search engine function, a replace function, etc.), acomplex function (e.g., compression, human and/or computer languagetranslation, text-to-voice conversion, voice-to-text conversion, etc.),multiple simple and/or complex functions, one or more algorithms, one ormore applications, etc. Hereafter, a storage unit may be interchangeablyreferred to as a dispersed storage and task (DST) execution unit and aset of storage units may be interchangeably referred to as a set of DSTexecution units.

Each of the computing devices 12-16, the managing unit 18, and theintegrity processing unit 20 include a computing core 26, which includesnetwork interfaces 30-33. Computing devices 12-16 may each be a portablecomputing device and/or a fixed computing device. A portable computingdevice may be a social networking device, a gaming device, a cell phone,a smart phone, a digital assistant, a digital music player, a digitalvideo player, a laptop computer, a handheld computer, a tablet, a videogame controller, and/or any other portable device that includes acomputing core. A fixed computing device may be a computer (PC), acomputer server, a cable set-top box, a satellite receiver, a televisionset, a printer, a fax machine, home entertainment equipment, a videogame console, and/or any type of home or office computing equipment.Note that each managing unit 18 and the integrity processing unit 20 maybe separate computing devices, may be a common computing device, and/ormay be integrated into one or more of the computing devices 12-16 and/orinto one or more of the storage units 36. In various embodiments,computing devices 12-16 can include user devices and/or can be utilizedby a requesting entity generating access requests, which can includerequests to read or write data to storage units in the DSN.

Each interface 30, 32, and 33 includes software and hardware to supportone or more communication links via the network 24 indirectly and/ordirectly. For example, interface 30 supports a communication link (e.g.,wired, wireless, direct, via a LAN, via the network 24, etc.) betweencomputing devices 14 and 16. As another example, interface 32 supportscommunication links (e.g., a wired connection, a wireless connection, aLAN connection, and/or any other type of connection to/from the network24) between computing devices 12 & 16 and the DSN memory 22. As yetanother example, interface 33 supports a communication link for each ofthe managing unit 18 and the integrity processing unit 20 to the network24.

Computing devices 12 and 16 include a dispersed storage (DS) clientmodule 34, which enables the computing device to dispersed storage errorencode and decode data as subsequently described with reference to oneor more of FIGS. 3-8. In this example embodiment, computing device 16functions as a dispersed storage processing agent for computing device14. In this role, computing device 16 dispersed storage error encodesand decodes data on behalf of computing device 14. With the use ofdispersed storage error encoding and decoding, the DSN 10 is tolerant ofa significant number of storage unit failures (the number of failures isbased on parameters of the dispersed storage error encoding function)without loss of data and without the need for a redundant or backupcopies of the data. Further, the DSN 10 stores data for an indefiniteperiod of time without data loss and in a secure manner (e.g., thesystem is very resistant to unauthorized attempts at accessing thedata).

In operation, the managing unit 18 performs DS management services. Forexample, the managing unit 18 establishes distributed data storageparameters (e.g., vault creation, distributed storage parameters,security parameters, billing information, user profile information,etc.) for computing devices 12-14 individually or as part of a group ofuser devices. As a specific example, the managing unit 18 coordinatescreation of a vault (e.g., a virtual memory block associated with aportion of an overall namespace of the DSN) within the DSN memory 22 fora user device, a group of devices, or for public access and establishesper vault dispersed storage (DS) error encoding parameters for a vault.The managing unit 18 facilitates storage of DS error encoding parametersfor each vault by updating registry information of the DSN 10, where theregistry information may be stored in the DSN memory 22, a computingdevice 12-16, the managing unit 18, and/or the integrity processing unit20.

The DSN managing unit 18 creates and stores user profile information(e.g., an access control list (ACL)) in local memory and/or withinmemory of the DSN memory 22. The user profile information includesauthentication information, permissions, and/or the security parameters.The security parameters may include encryption/decryption scheme, one ormore encryption keys, key generation scheme, and/or dataencoding/decoding scheme.

The DSN managing unit 18 creates billing information for a particularuser, a user group, a vault access, public vault access, etc. Forinstance, the DSN managing unit 18 tracks the number of times a useraccesses a non-public vault and/or public vaults, which can be used togenerate a per-access billing information. In another instance, the DSNmanaging unit 18 tracks the amount of data stored and/or retrieved by auser device and/or a user group, which can be used to generate aper-data-amount billing information.

As another example, the managing unit 18 performs network operations,network administration, and/or network maintenance. Network operationsincludes authenticating user data allocation requests (e.g., read and/orwrite requests), managing creation of vaults, establishingauthentication credentials for user devices, adding/deleting components(e.g., user devices, storage units, and/or computing devices with a DSclient module 34) to/from the DSN 10, and/or establishing authenticationcredentials for the storage units 36. Network administration includesmonitoring devices and/or units for failures, maintaining vaultinformation, determining device and/or unit activation status,determining device and/or unit loading, and/or determining any othersystem level operation that affects the performance level of the DSN 10.Network maintenance includes facilitating replacing, upgrading,repairing, and/or expanding a device and/or unit of the DSN 10.

The integrity processing unit 20 performs rebuilding of ‘bad’ or missingencoded data slices. At a high level, the integrity processing unit 20performs rebuilding by periodically attempting to retrieve/list encodeddata slices, and/or slice names of the encoded data slices, from the DSNmemory 22. For retrieved encoded slices, they are checked for errors dueto data corruption, outdated version, etc. If a slice includes an error,it is flagged as a ‘bad’ slice. For encoded data slices that were notreceived and/or not listed, they are flagged as missing slices. Badand/or missing slices are subsequently rebuilt using other retrievedencoded data slices that are deemed to be good slices to produce rebuiltslices. The rebuilt slices are stored in the DSN memory 22.

FIG. 2 is a schematic block diagram of an embodiment of a computing core26 that includes a processing module 50, a memory controller 52, mainmemory 54, a video graphics processing unit 55, an input/output (IO)controller 56, a peripheral component interconnect (PCI) interface 58,an IO interface module 60, at least one IO device interface module 62, aread only memory (ROM) basic input output system (BIOS) 64, and one ormore memory interface modules. The one or more memory interfacemodule(s) includes one or more of a universal serial bus (USB) interfacemodule 66, a host bus adapter (HBA) interface module 68, a networkinterface module 70, a flash interface module 72, a hard drive interfacemodule 74, and a DSN interface module 76.

The DSN interface module 76 functions to mimic a conventional operatingsystem (OS) file system interface (e.g., network file system (NFS),flash file system (FFS), disk file system (DFS), file transfer protocol(FTP), web-based distributed authoring and versioning (WebDAV), etc.)and/or a block memory interface (e.g., small computer system interface(SCSI), internet small computer system interface (iSCSI), etc.). The DSNinterface module 76 and/or the network interface module 70 may functionas one or more of the interface 30-33 of FIG. 1. Note that the IO deviceinterface module 62 and/or the memory interface modules 66-76 may becollectively or individually referred to as IO ports.

FIG. 3 is a schematic block diagram of an example of dispersed storageerror encoding of data. When a computing device 12 or 16 has data tostore it disperse storage error encodes the data in accordance with adispersed storage error encoding process based on dispersed storageerror encoding parameters. Here, the computing device stores data object40, which can include a file (e.g., text, video, audio, etc.), or otherdata arrangement. The dispersed storage error encoding parametersinclude an encoding function (e.g., information dispersal algorithm(IDA), Reed-Solomon, Cauchy Reed-Solomon, systematic encoding,non-systematic encoding, on-line codes, etc.), a data segmentingprotocol (e.g., data segment size, fixed, variable, etc.), and per datasegment encoding values. The per data segment encoding values include atotal, or pillar width, number (T) of encoded data slices per encodingof a data segment i.e., in a set of encoded data slices); a decodethreshold number (D) of encoded data slices of a set of encoded dataslices that are needed to recover the data segment; a read thresholdnumber (R) of encoded data slices to indicate a number of encoded dataslices per set to be read from storage for decoding of the data segment;and/or a write threshold number (W) to indicate a number of encoded dataslices per set that must be accurately stored before the encoded datasegment is deemed to have been properly stored. The dispersed storageerror encoding parameters may further include slicing information (e.g.,the number of encoded data slices that will be created for each datasegment) and/or slice security information (e.g., per encoded data sliceencryption, compression, integrity checksum, etc.).

In the present example, Cauchy Reed-Solomon has been selected as theencoding function (a generic example is shown in FIG. 4 and a specificexample is shown in FIG. 5); the data segmenting protocol is to dividethe data object into fixed sized data segments; and the per data segmentencoding values include: a pillar width of 5, a decode threshold of 3, aread threshold of 4, and a write threshold of 4. In accordance with thedata segmenting protocol, the computing device 12 or 16 divides dataobject 40 into a plurality of fixed sized data segments (e.g., 1 throughY of a fixed size in range of Kilo-bytes to Tera-bytes or more). Thenumber of data segments created is dependent of the size of the data andthe data segmenting protocol.

The computing device 12 or 16 then disperse storage error encodes a datasegment using the selected encoding function (e.g., Cauchy Reed-Solomon)to produce a set of encoded data slices. FIG. 4 illustrates a genericCauchy Reed-Solomon encoding function, which includes an encoding matrix(EM), a data matrix (DM), and a coded matrix (CM). The size of theencoding matrix (EM) is dependent on the pillar width number (T) and thedecode threshold number (D) of selected per data segment encodingvalues. To produce the data matrix (DM), the data segment is dividedinto a plurality of data blocks and the data blocks are arranged into Dnumber of rows with Z data blocks per row. Note that Z is a function ofthe number of data blocks created from the data segment and the decodethreshold number (D). The coded matrix is produced by matrix multiplyingthe data matrix by the encoding matrix.

FIG. 5 illustrates a specific example of Cauchy Reed-Solomon encodingwith a pillar number (T) of five and decode threshold number of three.In this example, a first data segment is divided into twelve data blocks(D1-D12). The coded matrix includes five rows of coded data blocks,where the first row of X11-X14 corresponds to a first encoded data slice(EDS 1_1), the second row of X21-X24 corresponds to a second encodeddata slice (EDS 2_1), the third row of X31-X34 corresponds to a thirdencoded data slice (EDS 3_1), the fourth row of X41-X44 corresponds to afourth encoded data slice (EDS 4_1), and the fifth row of X51-X54corresponds to a fifth encoded data slice (EDS 5_1). Note that thesecond number of the EDS designation corresponds to the data segmentnumber.

Returning to the discussion of FIG. 3, the computing device also createsa slice name (SN) for each encoded data slice (EDS) in the set ofencoded data slices. A typical format for a slice name 80 is shown inFIG. 6. As shown, the slice name (SN) 80 includes a pillar number of theencoded data slice (e.g., one of 1-T), a data segment number (e.g., oneof 1-Y), a vault identifier (ID), a data object identifier (ID), and mayfurther include revision level information of the encoded data slices.The slice name functions as, at least part of, a DSN address for theencoded data slice for storage and retrieval from the DSN memory 22.

As a result of encoding, the computing device 12 or 16 produces aplurality of sets of encoded data slices, which are provided with theirrespective slice names to the storage units for storage. As shown, thefirst set of encoded data slices includes EDS 1_1 through EDS 5_1 andthe first set of slice names includes SN 1_1 through SN 5_1 and the lastset of encoded data slices includes EDS 1_Y through EDS 5_Y and the lastset of slice names includes SN 1_Y through SN 5_Y.

FIG. 7 is a schematic block diagram of an example of dispersed storageerror decoding of a data object that was dispersed storage error encodedand stored in the example of FIG. 4. In this example, the computingdevice 12 or 16 retrieves from the storage units at least the decodethreshold number of encoded data slices per data segment. As a specificexample, the computing device retrieves a read threshold number ofencoded data slices.

To recover a data segment from a decode threshold number of encoded dataslices, the computing device uses a decoding function as shown in FIG.8. As shown, the decoding function is essentially an inverse of theencoding function of FIG. 4. The coded matrix includes a decodethreshold number of rows (e.g., three in this example) and the decodingmatrix in an inversion of the encoding matrix that includes thecorresponding rows of the coded matrix. For example, if the coded matrixincludes rows 1, 2, and 4, the encoding matrix is reduced to rows 1, 2,and 4, and then inverted to produce the decoding matrix.

FIG. 9A illustrates steps of an example of operation of securedistribution of one or more files amongst one or more computing devicesthat have already established trust. The managing unit 18 can issue afile list and integrity check information to devices of the DSN, wherethe file list includes an identifier list of system registry files fordistribution and where the integrity check information includes anintegrity value, such as a cryptographic hash value, for each fileand/or all system registry files associated with the file list. Theissuing includes obtaining the file list, generating the integrity checkinformation over corresponding system registry files associated with thefile list, and sending, via the network 24, the file list and integritycheck information to the devices of the DSN. Such DSN units can include,for example, storage units 36, integrity processing unit 20, and/orcomputing devices 12-16. In FIG. 9A, the DSN units include dispersedstorage and task (DST) execution units 1-n, which can be implemented byutilizing storage units 36 of FIG. 1, for example, operating as adistributed storage and task (DST) execution unit as describedpreviously, operable to store dispersed error encoded data and/or toexecute, in a distributed manner, one or more tasks on data.

Having received the file list, a DSN unit can issue a system filesstatus request to one or more other DSN units affiliated with the DSNunit when the DSN unit requires the system registry files associatedwith the file list (e.g., the system registry files are absent from theDSN unit). Issuing a system files request includes selecting the one ormore other DSN units generating the files based on the file list, andsending the files request to the selected one or more other DSN units.The selecting can be based on proximity with respect to the DSN unit(e.g., selecting DSN units that are closest), an expected networkloading level, a DST execution unit performance level, a networkperformance level, and/or DSN configuration information. For example,the processing module 84 of the DST execution unit 1 issues, via thenetwork 24, a system files status request to the other DST executionunits and to the managing unit 18 when the other DST execution units inthe managing unit 18 are located within a proximity threshold of the DSTexecution unit 1.

Having issued the system files status request, the DSN unit, within aresponse timeframe, can select a transmitting DSN unit based on acorresponding files response. For example, the DST execution unit 1selects the managing unit 18 when receiving a favorable files response(e.g., indicating that the system registry files are available) from themanaging unit 18 and receiving one or more unfavorable files responses(e.g., indicating that the system registry files are not available) fromthe other DST execution units.

Having selected the transmitting DSN unit, the DSN unit can send asystem files transmission request to the selected transmitting DSN unit.For example, the DSTN execution unit 1 generates and sends, via thenetwork 24, the system files transmission request to the DSTN managingunit 18. In response to the system files transmission request, the DSNunit receives the system registry files for storage. For example, theDST execution unit 1 receives, via the network 24, the system registryfiles from the DSTN managing unit 18.

Having received the system registry files, the DSN unit can validate thereceived system registry files based on one or more of the integritycheck information and the file list. The validating includes indicatingvalid when a calculated integrity check value compares favorably with areceived integrity check value for a portion of the system registryfiles. When the system registry files are validated, the DSN unitfacilitates local storage of the received system registry files. Forexample, as shown in FIG. 9A, the processing module 84 of the DSTexecution unit 1 can store the validated received system registry filesin the memory 88 of the DST execution unit 1. The processing module 84and memory 88 can be implemented utilizing the computing core of FIG. 2,for example, by specifically utilizing the processing module 50 and mainmemory 54 of the computing core. This protocol is secure against a DSNunit receiving an invalid file, assuming that no one can determine adifferent file that has the same hash value as one of the common files.This is an assumption for algorithms classified as cryptographicallysecure hash functions. In various embodiments, the DSN unit can send astatus transmission to other DSN units indicating that these systemregistry files are available. In various embodiments, the DSN unit cansend a verification error notification, for example for transmission tothe monitoring unit 18, when validation was unsuccessful.

FIG. 9B illustrates further steps of the example of operation of thedistributing of the one or more files, where a second DSN unit issues afiles request to one or more other DSN units affiliated with the secondDSN unit. For example, the processing module 84 of the DST executionunit 2 can issue, via the network 24, another system files statusrequest to the remaining DST execution units of the set of DST executionunits. Having sent the system files status request, within the responsetimeframe, the second DSN unit can select another transmitting DSN unitthat is storing the system registry files based on a corresponding filesresponse. For example, the DST execution unit 2 selects the DSTexecution unit 1 based on a favorable system files response from the DSTexecution unit 1 indicating that the system registry files are stored inthe memory 88 of the DST execution unit 1.

Having selected this second transmitting DSN unit, the second DSN unitsends another system files transmission request to this selectedtransmitting DSN unit. For example, the DST execution unit 2 can send,via the network 24, this system files transmission request to the DSTexecution unit 1 to initiate transmission of the system registry files.Having sent this system files transmission request, the second DSN unitcan receive the system registry files for storage. Having received thesystem registry files, the second DSN unit can validate the receivedsystem registry files based on the integrity check information and/orthe file list. When validated, the second DSN unit can store thevalidated received system registry files in a local memory associatedwith the second DSN unit. For example, the processing module 84 of theDST execution unit 2 stores the validated received system registry filesin the memory 88 of the DST execution unit 2.

In various embodiments, a processing system of a dispersed storage andtask (DST) execution unit includes at least one processor and a memorythat stores operational instructions, that when executed by the at leastone processor cause the processing system to receive system registryintegrity data via a network, where the system registry integrity datacorresponds to a plurality of system registry files. A request for asubset of the plurality of system registry files for is generated fortransmission to a first dispersed storage network (DSN) unit via thenetwork. The subset of the plurality of system registry files arereceived from the first DSN unit via the network. Integrity check datais generated based on the received subset of the plurality of systemregistry files and the system registry integrity data, where theintegrity check data includes a verification indicator. The systemregistry files are stored in memory when the verification indicatorindicates that verification was successful.

In various embodiments, the system registry integrity data includes aplurality of file identifiers corresponding to the plurality of systemregistry files and a plurality of integrity values corresponding to theplurality of system registry files. In various embodiments, theplurality of integrity values are cryptographic hash valuescorresponding to the plurality of system registry files. In variousembodiments, the integrity check data is generated by calculating atleast one integrity check value by performing a function on the receivedsubset of the plurality of system registry files, and comparing the atleast one integrity check value to a corresponding at least one of theplurality of integrity values of the system registry integrity data. Theverification indicator indicates that verification was successful whenthe at least one integrity check value compares favorably to thecorresponding at least one of the plurality of integrity values.

In various embodiments, a system files status request is generated fortransmission to a set of DSN units via the network, where the systemfiles status request indicates the subset of the plurality of systemregistry files. A plurality of system file statuses are received via thenetwork from at least one of the set of DSN units. The first DSN unit isselected from the set of DSN units based on the plurality of system filestatuses. In various embodiments, the set of DSN units are selected froma plurality of DSN units further based on proximity to the DST executionunit, an expected network loading level, a DST processing unitperformance level, a network performance level, and/or DSN configurationinformation. In various embodiments, the first DSN unit is selected fromthe set of DSN units in response to a one of the plurality of systemfile statuses corresponding to the first DSN unit indicating that thesubset of the plurality of system registry files are available. Invarious embodiments, a second DSN is selected from the set of DSN units,where a first one of the plurality of system file statuses correspondingto the first DSN unit and a second one of the plurality of system filestatuses corresponding to the second DSN unit indicate that a firstportion of the subset are available from the first DSN unit and a secondportion of the subset are available from the second DSN unit. The firstportion and the second portion collectively include all of the systemregistry files of the subset. A request for the second portion of thesubset is generated for transmission via the network to the second DSN,and the second portion of the subset is received in response via thenetwork.

In various embodiments, a verification error notification is generatedfor transmission via the network when the verification indicatorindicates that verification was unsuccessful. In various embodiments, asystem file status update is generated for transmission via the networkto a plurality of DSN units when the verification indicator indicatesthat verification was successful. The system file status updateindicates that the subset of the plurality of system registry files areavailable.

FIG. 10 is a flowchart illustrating an example of validating systemregistry files. In particular, a method is presented for use inassociation with one or more functions and features described inconjunction with FIGS. 1-9, for execution by a dispersed storage andtask (DST) execution unit that includes a processor or via anotherprocessing system of a dispersed storage network that includes at leastone processor and memory that stores instruction that configure theprocessor or processors to perform the steps described below. Step 1002includes receiving system registry integrity data via a network, wherethe system registry integrity data corresponds to a plurality of systemregistry files. Step 1004 includes generating a request for a subset ofthe plurality of system registry files for transmission to a firstdispersed storage network (DSN) unit via the network. Step 1006 includesreceiving the subset of the plurality of system registry files from thefirst DSN unit via the network. Step 1008 includes generating integritycheck data based on the received subset of the plurality of systemregistry files and the system registry integrity data, where theintegrity check data includes a verification indicator. Step 1010includes storing the system registry files in memory when theverification indicator indicates that verification was successful.

In various embodiments, the system registry integrity data includes aplurality of file identifiers corresponding to the plurality of systemregistry files and a plurality of integrity values corresponding to theplurality of system registry files. In various embodiments, theplurality of integrity values are cryptographic hash valuescorresponding to the plurality of system registry files. In variousembodiments, the integrity check data is generated by calculating atleast one integrity check value by performing a function on the receivedsubset of the plurality of system registry files, and comparing the atleast one integrity check value to a corresponding at least one of theplurality of integrity values of the system registry integrity data. Theverification indicator indicates that verification was successful whenthe at least one integrity check value compares favorably to thecorresponding at least one of the plurality of integrity values.

In various embodiments, a system files status request is generated fortransmission to a set of DSN units via the network, where the systemfiles status request indicates the subset of the plurality of systemregistry files. A plurality of system file statuses are received via thenetwork from at least one of the set of DSN units. The first DSN unit isselected from the set of DSN units based on the plurality of system filestatuses. In various embodiments, the set of DSN units are selected froma plurality of DSN units further based on proximity to the DST executionunit, an expected network loading level, a DST processing unitperformance level, a network performance level, and/or DSN configurationinformation. In various embodiments, the first DSN unit is selected fromthe set of DSN units in response to a one of the plurality of systemfile statuses corresponding to the first DSN unit indicating that thesubset of the plurality of system registry files are available. Invarious embodiments, a second DSN is selected from the set of DSN units,where a first one of the plurality of system file statuses correspondingto the first DSN unit and a second one of the plurality of system filestatuses corresponding to the second DSN unit indicate that a firstportion of the subset are available from the first DSN unit and a secondportion of the subset are available from the second DSN unit. The firstportion and the second portion collectively include all of the systemregistry files of the subset. A request for the second portion of thesubset is generated for transmission via the network to the second DSN,and the second portion of the subset is received in response via thenetwork.

In various embodiments, a verification error notification is generatedfor transmission via the network when the verification indicatorindicates that verification was unsuccessful. In various embodiments, asystem file status update is generated for transmission via the networkto a plurality of DSN units when the verification indicator indicatesthat verification was successful. The system file status updateindicates that the subset of the plurality of system registry files areavailable.

In various embodiments, a non-transitory computer readable storagemedium includes at least one memory section that stores operationalinstructions that, when executed by a processing system of a dispersedstorage network (DSN) that includes a processor and a memory, causes theprocessing system to receive system registry integrity data via anetwork, where the system registry integrity data corresponds to aplurality of system registry files. A request for a subset of theplurality of system registry files for is generated for transmission toa first dispersed storage network (DSN) unit via the network. The subsetof the plurality of system registry files are received from the firstDSN unit via the network. Integrity check data is generated based on thereceived subset of the plurality of system registry files and the systemregistry integrity data, where the integrity check data includes averification indicator. The system registry files are stored in memorywhen the verification indicator indicates that verification wassuccessful.

It is noted that terminologies as may be used herein such as bit stream,stream, signal sequence, etc. (or their equivalents) have been usedinterchangeably to describe digital information whose contentcorresponds to any of a number of desired types (e.g., data, video,speech, audio, etc. any of which may generally be referred to as‘data’).

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “configured to”, “operably coupled to”, “coupled to”, and/or“coupling” includes direct coupling between items and/or indirectcoupling between items via an intervening item (e.g., an item includes,but is not limited to, a component, an element, a circuit, and/or amodule) where, for an example of indirect coupling, the intervening itemdoes not modify the information of a signal but may adjust its currentlevel, voltage level, and/or power level. As may further be used herein,inferred coupling (i.e., where one element is coupled to another elementby inference) includes direct and indirect coupling between two items inthe same manner as “coupled to”. As may even further be used herein, theterm “configured to”, “operable to”, “coupled to”, or “operably coupledto” indicates that an item includes one or more of power connections,input(s), output(s), etc., to perform, when activated, one or more itscorresponding functions and may further include inferred coupling to oneor more other items. As may still further be used herein, the term“associated with”, includes direct and/or indirect coupling of separateitems and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that acomparison between two or more items, signals, etc., provides a desiredrelationship. For example, when the desired relationship is that signal1 has a greater magnitude than signal 2, a favorable comparison may beachieved when the magnitude of signal 1 is greater than that of signal 2or when the magnitude of signal 2 is less than that of signal 1. As maybe used herein, the term “compares unfavorably”, indicates that acomparison between two or more items, signals, etc., fails to providethe desired relationship.

As may also be used herein, the terms “processing module”, “processingcircuit”, “processor”, and/or “processing unit” may be a singleprocessing device or a plurality of processing devices. Such aprocessing device may be a microprocessor, micro-controller, digitalsignal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, and/or processing unit may be, or furtherinclude, memory and/or an integrated memory element, which may be asingle memory device, a plurality of memory devices, and/or embeddedcircuitry of another processing module, module, processing circuit,and/or processing unit. Such a memory device may be a read-only memory,random access memory, volatile memory, non-volatile memory, staticmemory, dynamic memory, flash memory, cache memory, and/or any devicethat stores digital information. Note that if the processing module,module, processing circuit, and/or processing unit includes more thanone processing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,and/or processing unit implements one or more of its functions via astate machine, analog circuitry, digital circuitry, and/or logiccircuitry, the memory and/or memory element storing the correspondingoperational instructions may be embedded within, or external to, thecircuitry comprising the state machine, analog circuitry, digitalcircuitry, and/or logic circuitry. Still further note that, the memoryelement may store, and the processing module, module, processingcircuit, and/or processing unit executes, hard coded and/or operationalinstructions corresponding to at least some of the steps and/orfunctions illustrated in one or more of the Figures. Such a memorydevice or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims. One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with other routines. In this context, “start” indicates thebeginning of the first step presented and may be preceded by otheractivities not specifically shown. Further, the “continue” indicationreflects that the steps presented may be performed multiple times and/ormay be succeeded by other activities not specifically shown. Further,while a flow diagram indicates a particular ordering of steps, otherorderings are likewise possible provided that the principles ofcausality are maintained.

The one or more embodiments are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical embodiment of an apparatus, an article ofmanufacture, a machine, and/or of a process may include one or more ofthe aspects, features, concepts, examples, etc. described with referenceto one or more of the embodiments discussed herein. Further, from figureto figure, the embodiments may incorporate the same or similarly namedfunctions, steps, modules, etc. that may use the same or differentreference numbers and, as such, the functions, steps, modules, etc. maybe the same or similar functions, steps, modules, etc. or differentones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theembodiments. A module implements one or more functions via a device suchas a processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

As may further be used herein, a computer readable memory includes oneor more memory elements. A memory element may be a separate memorydevice, multiple memory devices, or a set of memory locations within amemory device. Such a memory device may be a read-only memory, randomaccess memory, volatile memory, non-volatile memory, static memory,dynamic memory, flash memory, cache memory, and/or any device thatstores digital information. The memory device may be in a form a solidstate memory, a hard drive memory, cloud memory, thumb drive, servermemory, computing device memory, and/or other physical medium forstoring digital information.

While particular combinations of various functions and features of theone or more embodiments have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A method for execution by a processing systemthat includes a processor, the method comprises: generating a requestfor a plurality of system registry files; receiving the plurality ofsystem registry files via a network; generating a verification indicatorbased on an integrity check of the plurality of system registry filesversus system registry integrity data corresponding to the plurality ofsystem registry files; and storing the system registry files in memorywhen the verification indicator indicates that verification wassuccessful.
 2. The method of claim 1, wherein the system registryintegrity data includes a plurality of file identifiers corresponding tothe plurality of system registry files and a plurality of integrityvalues corresponding to the plurality of system registry files.
 3. Themethod of claim 2, wherein the plurality of integrity values arecryptographic hash values corresponding to the plurality of systemregistry files.
 4. The method of claim 2, wherein the verificationindicator is generated by calculating at least one integrity check valueby performing a function on the plurality of system registry files, andcomparing the at least one integrity check value to a corresponding atleast one of the plurality of integrity values of the system registryintegrity data, and wherein the verification indicator indicates thatverification was successful when the at least one integrity check valuecompares favorably to the corresponding at least one of the plurality ofintegrity values.
 5. The method of claim 1, further comprising:generating a system files status request for transmission to a set ofstorage units via the network, wherein the system files status requestindicates the plurality of system registry files; receiving a pluralityof system file statuses via the network from at least one of the set ofstorage units; selecting a first storage unit from the set of storageunits based on the plurality of system file statuses; and transmittingthe request for the plurality of system registry files to the firststorage unit.
 6. The method of claim 5, further comprising: selectingthe set of storage units from a plurality of storage units further basedon at least one of: proximity to the processing system, an expectednetwork loading level, a processing system performance level, a networkperformance level, or storage network configuration information.
 7. Themethod of claim 5, wherein the first storage unit is selected from theset of storage units in response to a one of the plurality of systemfile statuses corresponding to the first storage unit indicating thatthe plurality of system registry files are available.
 8. The method ofclaim 5, further comprising: selecting a second storage unit from theset of storage units, wherein a first one of the plurality of systemfile statuses corresponding to the first storage unit and a second oneof the plurality of system file statuses corresponding to the secondstorage unit indicate that a first portion of the plurality of systemregistry files are available from the first storage unit and a secondportion of the plurality of system registry files are available from thesecond storage unit, and wherein the first portion and the secondportion collectively include all of the system registry files of theplurality of system registry files; and generating a request for thesecond portion of the plurality of system registry files fortransmission via the network to the second storage unit and receivingthe second portion of the plurality of system registry files in responsevia the network.
 9. The method of claim 1, further comprising:generating a verification error notification for transmission via thenetwork when the verification indicator indicates that verification wasunsuccessful.
 10. The method of claim 1, further comprising: generatinga system file status update for transmission via the network to aplurality of storage units when the verification indicator indicatesthat verification was successful, wherein the system file status updateindicates that the plurality of system registry files are available. 11.A processing system of a dispersed storage and task (DST) execution unitcomprises: at least one processor; a memory that stores operationalinstructions, that when executed by the at least one processor cause theprocessing system to: generate a request for a plurality of systemregistry files; receive the plurality of system registry files via anetwork; generate a verification indicator based on an integrity checkof the plurality of system registry files versus system registryintegrity data corresponding to the plurality of system registry files;and store the system registry files in memory when the verificationindicator indicates that verification was successful.
 12. The processingsystem of claim 11, wherein the system registry integrity data includesa plurality of file identifiers corresponding to the plurality of systemregistry files and a plurality of integrity values corresponding to theplurality of system registry files.
 13. The processing system of claim12, wherein the plurality of integrity values are cryptographic hashvalues corresponding to the plurality of system registry files.
 14. Theprocessing system of claim 12, wherein the verification indicator isgenerated by calculating at least one integrity check value byperforming a function on the plurality of system registry files, andcomparing the at least one integrity check value to a corresponding atleast one of the plurality of integrity values of the system registryintegrity data, and wherein the verification indicator indicates thatverification was successful when the at least one integrity check valuecompares favorably to the corresponding at least one of the plurality ofintegrity values.
 15. The processing system of claim 11, wherein theoperational instructions, when executed by the at least one processor,further cause the processing system to: generating a system files statusrequest for transmission to a set of storage units via the network,wherein the system files status request indicates the plurality ofsystem registry files; receiving a plurality of system file statuses viathe network from at least one of the set of storage units; selecting afirst storage unit from the set of storage units based on the pluralityof system file statuses; and transmitting the request for the pluralityof system registry files to the first storage unit.
 16. The processingsystem of claim 15, wherein the operational instructions, when executedby the at least one processor, further cause the processing system to:select the set of storage units from a plurality of storage unitsfurther based on at least one of: proximity to the processing system, anexpected network loading level, a processing system performance level, anetwork performance level, or storage network configuration information.17. The processing system of claim 15, wherein the first storage unit isselected from the set of storage units in response to a one of theplurality of system file statuses corresponding to the first storageunit indicating that the plurality of system registry files areavailable.
 18. The processing system of claim 15, wherein theoperational instructions, when executed by the at least one processor,further cause the processing system to: select a second storage unitfrom the set of storage units, wherein a first one of the plurality ofsystem file statuses corresponding to the first storage unit and asecond one of the plurality of system file statuses corresponding to thesecond storage unit indicate that a first portion of the plurality ofsystem registry files are available from the first storage unit and asecond portion of the plurality of system registry files are availablefrom the second storage unit, and wherein the first portion and thesecond portion collectively include all of the system registry files ofthe plurality of system registry files; and generate a request for thesecond portion of the plurality of system registry files fortransmission via the network to the second storage unit and receivingthe second portion of the plurality of system registry files in responsevia the network.
 19. The processing system of claim 11, wherein theoperational instructions, when executed by the at least one processor,further cause the processing system to: generate a verification errornotification for transmission via the network when the verificationindicator indicates that verification was unsuccessful.
 20. Anon-transitory computer readable storage medium comprises: at least onememory section that stores operational instructions that, when executedby a processing system of a storage network that includes a processorand a memory, causes the processing system to: generate a request for aplurality of system registry files; receive the plurality of systemregistry files via a network; generate integrity check data based on theplurality of system registry files and system registry integrity datacorresponding to the plurality of system registry files, wherein theintegrity check data includes a verification indicator; and store thesystem registry files in memory when the verification indicatorindicates that verification was successful.